File Download Sequence
Whenever the Automatic Update feature is triggered (see Triggers for Automatic Update), the device attempts to download the files (if available) from the configured URLs in the following order:
|
3.
|
CLI Startup Script file |
|
4.
|
Periodic software file (.cmp) download |
|
5.
|
One-time software file (.cmp) download |
The following files instruct the device to restart:
|
■
|
CLI Startup Script file |
|
■
|
Periodic software file (.cmp) |
|
■
|
One-time software file (.cmp) |
When multiple files requiring a restart are downloaded, the device restarts only after it has downloaded and installed all the files. However, you can explicitly instruct the device to immediately restart for the following files:
|
■
|
ini file: Use the [ResetNow] in file parameter
|
|
■
|
CLI Script file: Use the reload if-needed CLI command |
If you use the [ResetNow] parameter in an ini file for periodic automatic provisioning with non-HTTP (e.g., TFTP) and without CRC, the device restarts after every file download. Therefore, use the parameter with caution and only if necessary for your deployment requirements.
|
●
|
For ini file downloads, parameters excluded from the file are set to default. To retain the current settings of these parameters, configure the [SetDefaultOnINIFileProcess] parameter to 0.
|
|
●
|
The CLI Startup Script file is not supported when the device operates in HA mode or if the Media Cluster feature is enabled. |
|
●
|
If you have configured one-time software file (.cmp) download (configured by the [CmpFileURL] parameter or CLI command configure system > automatic-update > firmware), the device will only apply the file if one-time software updates are enabled. This is disabled by default to prevent unintentional software upgrades. To enable one-time software upgrades, set the [AutoUpdateCmpFile] parameter to [1] or CLI command, configure system > automatic-update > update-firmware on. |
|
●
|
If you need to update the device's software and configuration, it is recommended to first update the software. This is because the current ("old") software (before the upgrade) may not be compatible with the new configuration. However, if both files are available for download on the provisioning server(s), the device first downloads and applies the new configuration, and only then does it download and install the new software. Therefore, this is a very important issue to take into consideration. |
|
●
|
If more than one file needs to be updated: |
|
✔
|
CLI Script and cmp: The device downloads and applies the CLI Script file on the currently ("old") installed software version. It then downloads and installs the cmp file with a restart. Therefore, the CLI Script file MUST have configuration compatible with the "old" software version. |
|
✔
|
CLI Startup Script and cmp: The device downloads both files, restarts, applies the new cmp, and then applies the configuration from the Startup Script file on the new software version. |
|
✔
|
CLI Script and Startup Script: The device downloads and applies both files; but the Startup Script file overwrites all the configuration of the CLI Script file. |
|
●
|
To configure the maximum time (timeout) allowed for downloading a file from the provisioning server, use the [AupdMaxTransferTime] parameter. |